Released on: December 9, 2007, 4:24 am

Press Release Author: Naeem Ismat

Industry: Industrial

Press Release Summary: Naeem Ismat, Automation Journalist reveals some very common
misunderstandings about OPC. Read entire editorial on following link....
http://www.automationmedia.com/EditorialsOld.asp?ID=185


Press Release Body: Do you know what OPC really stands for.. it does not stand for
\"Oooh.Please Connect\" and \"Old Programmers' Club\"
Actually OPC stand for - OLE for Process Control (where OLE is Object Linking and
Embedding). Some also say - Open Process Connectivity or simply OPC.

When end users or systems integrators move from traditional drivers to OPC servers,
sometime they have confusions about this new piece of software which they are going
to add in control system. Here are some of most common myths:

OPC "SERVER" and your new computer Specifications:
This is one of most common question asked to me during seminars, trainings and while
working with clients/SIs on systems topology. Most of end users from mangers,
engineers to guys on plant floor seem confusing on this name. Actually they try to
relate with IT servers class software and then thin about server class computer. I
noticed this name is equally confusing even for IT related staff as when setting up
specs for new projects they consider it as a SERVER. When we say OPC server it means
just another software on your computer. It is NOT like MS Server 2003. It is just
like any other computer software/utility. You are going to upgrade/replace your
vendor specific driver to a new driver which is now OPC compliant. This global
driver works same way as your original/old driver used to work for reading and
writing data to your controllers. So you can use any computer for your new OPC
SERVER. You may have to select powerful server class computer for you other HMI
SCADA or any other software which you are using, but not for OPC server. So, the PC
on which OPC Servers run doesn't have to be a Server class PC. Any standard PC works
fine. Any OPC server itself is not heavy application.

OPC "SERVER" Installation:
I also hear many question like "Does it required special expertise for
installation?". "Can I install it and setup in engineering department or I need to
call our IT ?". A typical OPC server installation is also a piece of cake and not
like any server class software (W200S or W2003S) installation. Overall installation
is very simple and straight forward. Most of vendors provide setup.exe file for opc
server installation. Double click on this file. Normally it prompts for very basic
and standard information like installation path, choice of installing OPC server
and/or opc client. Hit yes and installation will start. Normally it takes 2-5 min
on a "standard" computer. Sometime depending on vendor, installation may prompt you
for some additional features and components. In some case, vendor's SCADA software
installs driver during SCADA software installation and you don't need to install
separately. After installing OPC server, now your system can exchange data with any
other 3rd party OPC compliant software.


OPC and Protocol:
You will be using same protocol if you are upgrading/replacing your existing old
driver with OPC complaint server. The OPC Server does NOT replace your existing
protocol; you will still be using your existing protocols which may be Data Highway
Plus (DH+), Modbus RTU, ModbusPlus, ModbusEhtenet, Profibus or Ethernet/IP.

OPC and HMI/SCADA:
The HMI/SCADA systems only have to know one language - "OPC", which gives you many
choices. This is critical for your future needs. No more dependency on your existing
old system. If you are not happy with the performance of your current software or
support form vendor and decide to put another vendor's SCADA software at new area of
plant instead sticking with same vendor, you don't need to worry about data sharing.
All you need to make sure that new software is opc compliant and get any 3rd party
OCP server for you old systems. Companies like Matrikon, Kepware many others offer
opc servers for almost every software and protocols.

Before OPC, there were no standard for interfacing with devices, tools and
applications. Vendors must each develop their own proprietary servers.

With OPC, we have standard interface for applications to communicate, exchange data
and objects. Now vendors are developing to one standard OPC interface now.

Before OPC , we used to have custom interfaces which were costly, inefficient, risky.
Now with OPC, Client and Server write to a standard, reduced cost, protect
investment and we have more choices which is helping to increase productivity.



Web Site: http://www.automationmedia.com/EditorialsOld.asp?ID=185

Contact Details: Naeem Ismat
Naeem@AutomationMedia.com